Supersedes #180 (re-opened from keploy/java-sdk so the head ref lives in this repo instead of the fork).

Related Issue

• keploy/enterprise#1920

Related PRs

• keploy/enterprise#1912
• feat: add Java dynamic dedup sample samples-java#130
• docs: add Static Deduplication guide docs#841

Closes: NA

Describe the changes you've made

Rewrites the Java SDK repo to be dedup-only. The old record/test/grpc/integration SDK modules are deleted; the remaining published module is keploy-sdk for Java dynamic dedup replay support.

• Adds KeployDedupAgent for Enterprise dynamic dedup using /tmp/coverage_control.sock and /tmp/coverage_data.sock.
• Handles per-testcase START <test-set>/<test-id> by resetting JaCoCo counters.
• Handles matching END <test-set>/<test-id> by dumping/resetting JaCoCo execution data, analyzing app classes, publishing {id, executedLinesByFile}, and ACKing Enterprise.
• Reads JaCoCo coverage in-process via the runtime API (org.jacoco.agent.rt.RT.getAgent().getExecutionData(...)) using reflection, so consumers do not need JaCoCo TCP server mode or --pass-through-ports.
• Falls back to JaCoCo TCP server mode when the runtime API is unavailable; KEPLOY_JACOCO_HOST and KEPLOY_JACOCO_PORT still configure that fallback.
• Discovers executable Spring Boot/fat jars from sun.java.command, which fixes Docker layouts where java.class.path does not include the runnable jar.
• Keeps replay fast by caching class metadata, prioritizing explicit class dirs, and avoiding broad classpath fallback unless KEPLOY_JAVA_CLASSPATH_FALLBACK=true is set.
• Keeps the servlet middleware only as a lifecycle hook for javax.servlet; Jakarta/Spring Boot 3 and non-servlet apps can call KeployDedupAgent.start() directly.
• Updates the README to describe native, Docker, restricted Docker, and socket requirements for dedup-only usage.

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Code style update (formatting, local variables)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How did you test your code changes?

• mvn -B -DskipTests clean verify -pl keploy-sdk -am on JDK 8.
• mvn -B -DskipTests clean verify -pl keploy-sdk -am on JDK 17.
• mvn -B -DskipTests clean verify -pl keploy-sdk -am on JDK 21.
• mvn -B -DskipTests -Dgpg.skip=true clean install -pl keploy-sdk -am for the local sample app build.
• git diff --check.
• Validated with samples-java/java-dedup against 1000 committed replay fixtures in Docker Compose: 1000 successes, 0 failures.
• Validated with samples-java/java-dedup against 1000 committed replay fixtures in direct docker run: 1000 successes, 0 failures.
• Confirmed keploy dedup --path . produced 982 duplicates and 18 retained tests.

No unit tests were added by request; validation is build and replay coverage.

Describe if there is any unusual behaviour of your code(Write NA if there isn't)

Java dedup attaches the JaCoCo Java agent and reads coverage in-process by default. If the in-process API cannot be located, the SDK falls back to JaCoCo's TCP server mode automatically. Docker and restricted Docker modes still require Enterprise and application containers/processes to share /tmp so the control/data Unix sockets are visible.

Checklist:

• My code follows the style guidelines of this project.
• I have performed a self-review of my own code.
• I have commented my code, particularly in hard-to-understand areas and used java doc.
• I have made corresponding changes to the documentation.
• My changes generate no new warnings.
• I have added tests that prove my fix is effective or that my feature works.
• New and existing unit tests pass locally with my changes.

Screenshots (if any)

NA